Minutes, IBIS Quality Task Group 25 July 2017 11:00-12:00 EST (08:00-09:00 PST) ROLL CALL eASIC: David Banas Ericsson: Anders Ekholm Intel: * Michael Mirmak Eugene Lim IO Methodology: * Lance Wang Signal Integrity Software: * Mike LaBonte Teraspeed Labs: * Bob Ross Visteon: Preetesh Rathod Everyone in attendance marked by * NOTE: "AR" = Action Required. -----------------------MINUTES --------------------------- Mike LaBonte conducted the meeting. Call for IBIS related patent disclosures: - None Call for opens: - None Review of previous meeting minutes: - Bob Ross moved to approve minutes from the July 18 meeting. Mike LaBonte seconded the motion. Minutes were approved without objection. ARs: - Mike LaBonte to run TBD testcase with -numbered and submit to Bob Ross - Done. - Bob Ross to write bug reports for new issues - Some work done, will review today. - Mike LaBonte to write text for contract to complete IBISCHK message help. - Deferred until next parser release. New IBISCHK6 bugs: - Bob: BUG 190 will be about changing a node connection error to a warning. - It affects multi-lingual models. - Mike L: We need to be sure no specification change is needed. - Bob showed bug191.txt - Bob: A signal port is required but not present. - Another example is missing an A_to_D. - The third example has an extra port, unused. - A misleading message implies that it is Corner related, but it is not. - Mike L: The message should not mention Corner. - Bob: In IN3 a signal is incorrectly flagged as illegal. - Mike L: That is a false positive, higher priority. - Bob: In IN4 an "unused port" error causes two other irrelevant errors. - The first one should be a warning. - Bob: The dummy subcircuit is present in the testcase but not really checked. - It is marked ANNOYING and LOW - Mike L: One of the bugs is a false positive, will users possibly be stuck? - The severity probably should be MODERATE> - Bob: We probably do not have enough bugs to produce a 6.1.5 parser. - There will be a lot of work for BIRD 189 - Michael M: We should have [Ramp] dV checked against [Voltage Range] - This is a common problem with AMI models. - They have IV but no VT - They have bogus [Ramp] dV but no error is flagged. - Bob: The parser checks for that - Michael M: I was previously told the parser need not check this because industry tools check it. - Mike L: Maybe -caution enables that check. - Michael M: I tested, it does indeed produce a CAUTION. - Bob Ross moved to adjourn. Michael M. seconded. The meeting ended without objection. Meeting ended: 11:45 ET Next meeting August 1, 2017